Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release #1901

Merged
merged 34 commits into from
Dec 6, 2023
Merged

Release #1901

merged 34 commits into from
Dec 6, 2023

Conversation

bill-long
Copy link
Member

No description provided.

Shanefe and others added 30 commits November 22, 2023 11:43
Queue viewer crash
Fixing formatting with URL
Add High Performance (ConfigMgr) power plan detection to HC
Adding logic for Publishing

Format tables

Output cmdlet calls
Adding logic for Publishing

Format tables

Output cmdlet calls

Skip checks if they are not using modern sharing

Output Sharing specifically at bottom
Code standards
Adding Output of Sharing Type specifically
Output changes and parameter for waiting time in Test-ExchAVExclusions
dpaulson45 and others added 4 commits December 6, 2023 10:06
Save RBA Log, RBA Logs summary, Better coverage of known issues
In previous versions of VSSTester, the user had to specify a
database when testing a DiskShadow backup. This would cause
VSSTester to look up the volumes that stored the database
and log files, and then it would snap those volumes.

This approach works for most cases, but it makes it hard to compare
with backup software that only allows specifying volumes, not
databases.

This change allows running a DiskShadow backup of specified
volumes. To get a list of acceptable volume names, the user can
specify one that is invalid. For example:

```
[PS] C:\>.\VSSTester.ps1 -DiskShadow -VolumesToBackup foo
C:\VSSTester.ps1 : Cannot validate argument on parameter 'VolumesToBackup'. Invalid volume specified. Please specify one of the
following values:
C:\
C:\Databases\DB1\
At line:1 char:70
+ ... code\CSS-Exchange\dist\VSSTester.ps1 -DiskShadow -VolumesToBackup foo
```

One or two volumes can be specified. As usual, drive letters must be
provided. For this syntax, the number of provided drive letters must
match the number of specified volumes. Example:

```
VSSTester.ps1 -DiskShadow -VolumesToBackup C:\Databases\DB1\ -ExposeSnapshotsOnDriveLetters X
```

This PR includes several other changes:

* Get-WmiObject has been replaced with Get-CimInstance.
* Drive letters are now specified with -ExposeSnapshotsOnDriveLetters,
  which more clearly communicates the intent and allows specifying
  one or more drive letters with a single parameter.
VSSTester: Allow specifying volumes to back up
@bill-long bill-long merged commit 38d6a31 into release Dec 6, 2023
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants